with untrusted guests. If a policy is provided by the bootloader, it will be
loaded; errors will be reported to the ring buffer but will not prevent
booting. The policy can be changed to enforcing mode using "xl setenforce".
-* `enforcing`: This will cause the security server to enter enforcing mode prior
- to the creation of domain 0. If an valid policy is not provided by the
- bootloader and no built-in policy is present, the hypervisor will not continue
- booting.
-* `late`: This disables loading of the built-in security policy or the policy
- provided by the bootloader. FLASK will be enabled but will not enforce access
- controls until a policy is loaded by a domain using "xl loadpolicy". Once a
- policy is loaded, FLASK will run in enforcing mode unless "xl setenforce" has
- changed that setting.
+* `enforcing`: This requires a security policy to be provided by the bootloader
+ and will enter enforcing mode prior to the creation of domain 0. If a valid
+ policy is not provided, the hypervisor will not continue booting.
+* `late`: This disables loading of the security policy from the bootloader.
+ FLASK will be enabled but will not enforce access controls until a policy is
+ loaded by a domain using "xl loadpolicy". Once a policy is loaded, FLASK will
+ run in enforcing mode unless "xl setenforce" has changed that setting.
* `disabled`: This causes the XSM framework to revert to the dummy module. The
dummy module provides the same security policy as is used when compiling the
hypervisor without support for XSM. The xsm\_op hypercall can also be used to
system_r for all domains.
The FLASK security framework is mostly configured using a security policy file.
-It relies on the SELinux compiler "checkpolicy"; if this is available, the
-policy will be compiled as part of the tools build. If hypervisor support for a
-built-in policy is enabled ("Compile Xen with a built-in security policy"), the
-policy will be built during the hypervisor build.
-
-The policy is generated from definition files in tools/flask/policy. Most
-changes to security policy will involve creating or modifying modules found in
-tools/flask/policy/modules/. The modules.conf file there defines what modules
-are enabled and has short descriptions of each module.
-
-If not using the built-in policy, the XSM policy file needs to be copied to
-/boot and loaded as a module by grub. The exact position and filename of the
-module does not matter as long as it is after the Xen kernel; it is normally
-placed either just above the dom0 kernel or at the end. Once dom0 is running,
-the policy can be reloaded using "xl loadpolicy".
+This policy file is not normally generated during the Xen build process because
+it relies on the SELinux compiler "checkpolicy"; run
+
+ make -C tools/flask/policy
+
+to compile the example policy included with Xen. The policy is generated from
+definition files under this directory. Most changes to security policy will
+involve creating or modifying modules found in tools/flask/policy/modules/. The
+modules.conf file there defines what modules are enabled and has short
+descriptions of each module.
+
+The XSM policy file needs to be copied to /boot and loaded as a module by grub.
+The exact position of the module does not matter as long as it is after the Xen
+kernel; it is normally placed either just above the dom0 kernel or at the end.
+Once dom0 is running, the policy can be reloaded using "xl loadpolicy".
The example policy included with Xen demonstrates most of the features of FLASK
that can be used without dom0 disaggregation. The main types for domUs are:
*(.init.data.rel)
*(.init.data.rel.*)
- __xsm_init_policy_start = .;
- *(.init.xsm_policy)
- __xsm_init_policy_end = .;
-
. = ALIGN(8);
__ctors_start = .;
*(.init_array)
*(.init.data)
*(.init.data.rel)
*(.init.data.rel.*)
-
- __xsm_init_policy_start = .;
- *(.init.xsm_policy)
- __xsm_init_policy_end = .;
-
. = ALIGN(4);
__trampoline_rel_start = .;
*(.trampoline_rel)
If unsure, say Y.
-config XSM_POLICY
- bool "Compile Xen with a built-in security policy"
- default y
- depends on XSM
- ---help---
- This includes a default XSM policy in the hypervisor so that the
- bootloader does not need to load a policy to get sane behavior from an
- XSM-enabled hypervisor. If this is disabled, a policy must be
- provided by the bootloader or by Domain 0. Even if this is enabled, a
- policy provided by the bootloader will override it.
-
- This requires that the SELinux policy compiler (checkpolicy) be
- available when compiling the hypervisor; if this tool is not found, no
- policy will be added.
-
- If unsure, say Y.
-
# Enable schedulers
menu "Schedulers"
visible if EXPERT = "y"
$(AV_H_FILES): $(AV_H_DEPEND)
$(CONFIG_SHELL) policy/mkaccess_vector.sh $(AWK) $(AV_H_DEPEND)
-ifeq ($(CONFIG_XSM_POLICY),y)
-HAS_CHECKPOLICY := $(shell checkpolicy -h 2>&1 | grep -q xen && echo y || echo n)
-
-obj-$(HAS_CHECKPOLICY) += policy.o
-endif
-
-LDFLAGS += --accept-unknown-input-arch
-
-POLICY_SRC := $(XEN_ROOT)/tools/flask/policy/xenpolicy-$(XEN_FULLVERSION)
-
-policy.bin: FORCE
- $(MAKE) -C $(XEN_ROOT)/tools/flask/policy
- cmp -s $(POLICY_SRC) $@ || cp $(POLICY_SRC) $@
-
-policy.o: policy.bin
- $(OBJCOPY) -S -I binary -O elf64-little --rename-section=.data=.init.xsm_policy $< $@
-
.PHONY: clean
clean::
rm -f $(ALL_H_FILES) *.o $(DEPS)
return 0;
}
-extern char __xsm_init_policy_start[], __xsm_init_policy_end[];
-
-static void __init xsm_policy_init(void)
-{
- if ( policy_size == 0 && __xsm_init_policy_end != __xsm_init_policy_start )
- {
- policy_buffer = __xsm_init_policy_start;
- policy_size = __xsm_init_policy_end - __xsm_init_policy_start;
- }
-}
-
static int __init xsm_core_init(void)
{
if ( verify(&dummy_xsm_ops) )
}
xsm_ops = &dummy_xsm_ops;
- xsm_policy_init();
flask_init();
return 0;
ret = xsm_core_init();
- if ( policy_buffer != __xsm_init_policy_start )
- xfree(policy_buffer);
+ xfree(policy_buffer);
return ret;
}
projects / xen.git / commitdiff